Skip to content

Update oauth-client-credentials.mdx#9

Open
pcarleton wants to merge 3 commits intomainfrom
pcarleton-patch-1
Open

Update oauth-client-credentials.mdx#9
pcarleton wants to merge 3 commits intomainfrom
pcarleton-patch-1

Conversation

@pcarleton
Copy link
Member

Oauth 2.1 2.4.1 is about client id and secret:
https://www.ietf.org/archive/id/draft-ietf-oauth-v2-1-13.html#section-2.4.1

To support clients in possession of a client secret, the authorization server MUST support the client including the client credentials in the request body content using the following parameters:

"client_id":
REQUIRED. The client identifier issued to the client during the registration process described by Section 2.2.

"client_secret":
REQUIRED. The client secret.

But I think we want to explicitly reference the Client Credentials grant in 4.2:

The client can request an access token using only its client credentials (or other supported means of authentication) when the client is requesting access to the protected resources under its control, or those of another resource owner that have been previously arranged with the authorization server (the method of which is beyond the scope of this specification).

@pcarleton pcarleton requested a review from a team November 24, 2025 21:25
@tulshi
Copy link

tulshi commented Feb 18, 2026

This PR is a bit confusing. I see @pcarleton's initial comment that we should be talking about client credentials and not the "client secret", but the PR itself only changes the URL that is referred to from the client secret section. The section referred to from line 61 in this PR doesn't actually talk about "Clients use a Client Secret transmitted in the request content " as the text before the link says. Am I missing something?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants